#Source Code Management
Explore tagged Tumblr posts
Text
Source code management
What is source code management?
It allows a developer to organize code iterations chronologically, and version it for an application. The most powerful features of source code management systems are in how they allow teams of very diverse sizes to work together on the same application simultaneously.
Some terms that are common to all of them:
A project will be called repository, it’s representing the index/the filesystem root of your project.
Developers might create branches of the codebase, that they will iterate on separately to other developers. For instance, a branch can be meant to be used for a given feature, or a given bug fix. One can create however many branches they need.
Once a branch is ready for it (it’s been tested, peer-reviewed, etc.), it can be merged back to the main branch. The main branch may be called differently: in Git it’s called master , in SVN it’s called trunk.
While coding on their branch, developers are meant to work in small, atomic iterations, called commits. All commits have a commit message describing in one sentence what’s in there.
All commits together are called the history , and it’s a big deal to write meaningful commits and commit messages in order to keep the project’s history clean at a glance, to understand what has been going on and who did what.
Some people might be modifying the same pieces on the codebase on different branches, and this could create conflicts when one merges those branches together. Some of those conflicts can obviously only be fixed by a human, and each system has a different way to manage merge conflicts.
Which systems exist?
I’ll put each specific wording between quotes. The same words may be used for differing notions across the various products.
SourceSafe was an early source code management system from Microsoft, which didn’t handle branches, merges, or conflicts. You could “check out” a file, which meant no one else was allowed to “check it out” and modify it at the same time. When you were done with it, you could “check in” the file, making it editable again to the others. Not very suitable for large teams that may work on the same file, and longer iterations in a given file. SourceSafe is discontinued today.
CVS was among the first open-source source code management systems in the industry, and used to be wildly popular, but is barely seen anymore. It didn’t handle branches, but two people could modify the same file at the same time. People would “update” their whole directory to get everybody else’s work before starting, and “commit” their code to the server when they’re done. When they would “commit” a file that had been “committed” by someone else since last time they “updated”, the system was not able to merge, so it would consider it a conflict every time, that you would have to manually fix (even if the changes were not on the same lines, for instance).
SVN was built upon CVS to handle branches, so a lot of terminology is the same. At some point, it was the most used system, and it is still seen in the industry, even though people are walking away from it. When you’d create a branch, it would actually copy-paste the whole codebase into another directory in the code repository; then, you’d try to merge, and it would massively compare each file one by one. Merging algorithms were smarter than the CVS ones, but you still had conflicts on most merges, even those that shouldn’t necessarily require a human. When you’d create a “tag” (which is a set version of your code, like “1.2.0”), then the whole codebase would simply be massively copy-pasted into another directory too, but without the intention to merge it back later.
Git doesn’t copy-paste the whole codebase when branching and tagging, but stores each commit as a code iteration, in an organized structure that resembles a tree. This allows it to have a much smarter merging algorithm, and it almost never bothers you with conflicts, except for those that really need a human decision. As a result, the cost of branching/merging is very low, and people typically branch/merge a lot, therefore one should never directly work on the “master” branch, if they’re not the only developer on the project. Also: unlike its predecessors, Git allows to work and commit without needing to talk with a server, which allows to work on planes, for instance; and it also can work as a decentralized (peer-to-peer) system, although it’s very rarely done that way.
Mercurial is very similar to Git in its concepts (although the syntax of its command-line tool is often different). It is more rarely seen in the industry than Git, but is still very relevant. It is the one used by Facebook, for instance, for its main application.
The lowdown on Git
A particularity about Git, is that it’s designed to be useable without a central repository (you can pull code from your friend’s computer, and push you work back there, for instance), but not many people use it that way. There is usually a central Git server that the whole team pushes code to and pulls code from; however, that explains why it is often referred as a “decentralized” system.
So that you can work without a server, the commit operation is local, no one other than your computer knows you committed something. You can make several commits however you want, but when you want the server to know about it, you must push them there. You want to be pulling from the repository often if other people may be working on the same branch as you, because each pull performs a merge operation between the code you didn’t have, and the code you recently committed locally. Therefore, in order to let you push , Git will sometimes demand that you pull first, so that the merge can be done on your computer, and you take care of potential conflicts.
Sometimes, you may have modified 3 files, but there are only two that you wish to include in the commit you’re about the make. Therefore, Git has a notion of “ index”, in which you add your modified files so that they’re included in the next commit you register.
How to configure the remote servers your local repository is talking to? They’re called remotes , and you can configure however many you need. The main one is typically named origin (that’s the name that is setup by default when you clone a project from a remote location in the first place). You can also configure however many branches you need, and name them as you please, and the default one is usually called master.
Some UI tools for Git exist, but Git is able to do so many things, that they don’t represent the magnitude of cases for which you need Git. You really want to learn to use it with the command line. Here are some commands:
$ git clone url_of_your_remote_repository # Clone a repository from a remote repository $ git add file1 file2 # will add those two files to the index if they were modified $ git commit -m "Meaningful commit message" # will commit those two files (locally) $ git add . # will add all of the modified files to the index at once $ git commit -m "Other meaningful commit message" # will commit all of those files together $ git push origin master # send all commit to the remote server
Now, let’d do this again, but by on a branch:
$ git branch my_feature # Creating the branch $ git checkout my_feature # Changing the codebase so that we're on that branch now $ git checkout -b my_feature # This does the two previous operations in one ;) $ git add file1 file2 $ git commit -m "Meaningful commit message" # We didn't just commit this on the master branch like last time, but on the my_feature one $ git add . $ git commit -m "Other meaningful commit message" $ git push origin my_feature # Notice, we're not pushing master anymore, you just create a new remote branch
Next time you want to work on that branch, you should probably do this first:
$ git checkout my_feature # Just making sure you're currently on the right branch! $ git pull origin my_feature # Pulling what your coworkers have done so far.
And when you’re done with the whole feature and want to merge it to master:
$ git checkout master $ git merge my_feature
One other pretty neat thing: if you have a non-Git directory in your computer, and you want to turn it into a Git repository, it’s that easy:
$ git init # You're done! $ git remote add origin url_of_your_git_server # So that you can push your code somewhere.
When you’re in a Git repository, and want to know which files are modified but not in the index, and those that are modified and are in the index, you can run:
$ git status
Git provides many more abilities, such as rewriting pieces of the history of the project if you feel the commits were not meaningful enough, displaying the history in visually meaningful ways, …
For instance, you should run this right now, and see how a complex history can be viewed really nicely:
$ git clone [https://github.com/loverajoel/jstips.git](https://github.com/loverajoel/jstips.git) # You will need a GitHub account for this to work $ cd jstips # changing your directory into the one you just downloaded $ git log --graph --pretty=tformat:'%Cred%h%Creset -%C(yellow)%d%Creset %s %Cgreen(%an %cr)%Creset' --abbrev-commit --date=relative
Cool, right?
What is the difference between Git and GitHub?
Git is everything we’ve covered so far: a source code management tool, that comes with a command-line tool for its users.
GitHub is one of many services that provide at the same time:
a Git repository server to push your code to
a web UI to that view your repositories, with their files and commits
a number of extra features (managing your team and accesses, …) Two GitHub features you have to get familiarized with are:
Forks : you can fork any repository on GitHub, and it will duplicate the repository’s codebase into repository that you own. For instance, if you fork twbs/bootstrap, and your GitHub username is “my_username”, then it will create the my_username/bootstrap repository, and it will remember where it was forked from. Usually, you aren’t allowed to push on other people’s repositories, so that will give you a repository that you can push to, since you own it.
Pull requests: once you’ve pushed your code to your repository (or sometimes to a branch of the main repository, if you’re allowed), then you can create a pull request towards the main repository’s master branch. Somebody in charge of the main repository will review your pull request (potentially asking you to change a couple of things), and merge it if it’s suitable to be in the main product.
GitHub has many competitors, two of the main ones being GitLab and BitBucket (which provide very similar services). We chose to make you use GitHub because that’s where most of the industry is (that way, you’ll be able to interact with them on their open-source projects), and it’s also where tech recruiters typically go check out to see what you’ve been up to.
Some interesting links about Git
https://try.github.io: an interactive tutorial for beginners.
https://help.github.com/articles/good-resources-for-learning-git-and-github/: a list of resources about Git, curated by GitHub.
http://nvie.com/posts/a-successful-git-branching-model/: once you master the technical tool, you have many ways to organize your branches according to your project. This very notorious article from 2010 introduces git-flow , a detailed proposal for organizing collective work with Git that is still the most common today. You should talk about that each time you start a collaborative project using Git.
http://semver.org: now that you can give version numbers to your code iterations, how should you number them? Semantic versioning is the most used versioning scheme.
Git from the inside out
Learn git branching
0 notes
Text
Driving Innovation: A Case Study on DevOps Implementation in BFSI Domain
Banking, Financial Services, and Insurance (BFSI), technology plays a pivotal role in driving innovation, efficiency, and customer satisfaction. However, for one BFSI company, the journey toward digital excellence was fraught with challenges in its software development and maintenance processes. With a diverse portfolio of applications and a significant portion outsourced to external vendors, the company grappled with inefficiencies that threatened its operational agility and competitiveness. Identified within this portfolio were 15 core applications deemed critical to the company’s operations, highlighting the urgency for transformative action.
Aspirations for the Future:
Looking ahead, the company envisioned a future state characterized by the establishment of a matured DevSecOps environment. This encompassed several key objectives:
Near-zero Touch Pipeline: Automating product development processes for infrastructure provisioning, application builds, deployments, and configuration changes.
Matured Source-code Management: Implementing robust source-code management processes, complete with review gates, to uphold quality standards.
Defined and Repeatable Release Process: Instituting a standardized release process fortified with quality and security gates to minimize deployment failures and bug leakage.
Modernization: Embracing the latest technological advancements to drive innovation and efficiency.
Common Processes Among Vendors: Establishing standardized processes to enhance understanding and control over the software development lifecycle (SDLC) across different vendors.
Challenges Along the Way:
The path to realizing this vision was beset with challenges, including:
Lack of Source Code Management
Absence of Documentation
Lack of Common Processes
Missing CI/CD and Automated Testing
No Branching and Merging Strategy
Inconsistent Sprint Execution
These challenges collectively hindered the company’s ability to achieve optimal software development, maintenance, and deployment processes. They underscored the critical need for foundational practices such as source code management, documentation, and standardized processes to be addressed comprehensively.
Proposed Solutions:
To overcome these obstacles and pave the way for transformation, the company proposed a phased implementation approach:
Stage 1: Implement Basic DevOps: Commencing with the implementation of fundamental DevOps practices, including source code management and CI/CD processes, for a select group of applications.
Stage 2: Modernization: Progressing towards a more advanced stage involving microservices architecture, test automation, security enhancements, and comprehensive monitoring.
To Expand Your Awareness: https://devopsenabler.com/contact-us
Injecting Security into the SDLC:
Recognizing the paramount importance of security, dedicated measures were introduced to fortify the software development lifecycle. These encompassed:
Security by Design
Secure Coding Practices
Static and Dynamic Application Security Testing (SAST/DAST)
Software Component Analysis
Security Operations
Realizing the Outcomes:
The proposed solution yielded promising outcomes aligned closely with the company’s future aspirations. Leveraging Microsoft Azure’s DevOps capabilities, the company witnessed:
Establishment of common processes and enhanced visibility across different vendors.
Implementation of Azure DevOps for organized version control, sprint planning, and streamlined workflows.
Automation of builds, deployments, and infrastructure provisioning through Azure Pipelines and Automation.
Improved code quality, security, and release management processes.
Transition to microservices architecture and comprehensive monitoring using Azure services.
The BFSI company embarked on a transformative journey towards establishing a matured DevSecOps environment. This journey, marked by challenges and triumphs, underscores the critical importance of innovation and adaptability in today’s rapidly evolving technological landscape. As the company continues to evolve and innovate, the adoption of DevSecOps principles will serve as a cornerstone in driving efficiency, security, and ultimately, the delivery of superior customer experiences in the dynamic realm of BFSI.
Contact Information:
Phone: 080-28473200 / +91 8880 38 18 58
Email: [email protected]
Address: DevOps Enabler & Co, 2nd Floor, F86 Building, ITI Limited, Doorvaninagar, Bangalore 560016.
#BFSI#DevSecOps#software development#maintenance#technology stack#source code management#CI/CD#automated testing#DevOps#microservices#security#Azure DevOps#infrastructure as code#ARM templates#code quality#release management#Kubernetes#testing automation#monitoring#security incident response#project management#agile methodology#software engineering
0 notes
Text
update: local lesbian forced to learn at least very basic coding. 7 dead 32 injured
#.txt#this is not for new perspectives unfortunately#this is bc i realized that actually i am much more prone to remember things in my routine when i am verbally reminded#and i cannot expect other people to manage my schedule so it would be v beneficial for me to have some kind of virtual assistant device#but i refuse to have alexa or any type of apple + google device listening in my home for Many reasons#long story short i'm going to be trying to work with an open source software i found online to put something together that suits My needs#but i'm defo going to need to sit my ass down and do some Actual learning re programming#and not the fake coding i've been slapping together for new perspectives#sighhhhh#oh well
4 notes
·
View notes
Note
Watched the Rain Code trailers today and I died inside like 5 times because of 2 of the VAs and Twilight's voice. I DID SOBBED REALIZING THE VA OF MY FAVOURITE CHARACTER WAS THERE TOO
ASANO RAIN CODE ERA LETS GO!!!
#guess what i like crammed spaces in this source too :3#my gay yearning managed to spread rain code propaganda thats great#-The Evangelist of Murder. Killer Killer#KillerKiller.txt
5 notes
·
View notes
Text
are y'all ever listening to a youtube video and immediately just go "oh im in way too deep"
#truthfully tho the zelda theory community is amazing#this man was talking about zelda project code names being Edward and Richard and shit and he managed to convince me#PLUS ganon is energy source confirmed?? im buying everyone a round of drinks we did it lads
3 notes
·
View notes
Text
NO I KNEW I WASN'T LOSING MY MIND!! I KNEW I REMEMBERED READING THAT THEY WANTED TO HAVE AS MUCH OF TUMBLR AS OPEN SOURCE AS POSSIBLE
tweet thats mentioning it, from november last year
if I could remember or find the article that mentioned the sites coding being what's made it take so long (not worded like that)....
#[ ;text ]#as much of tumblr to be open source as possible#which DOES lead me to think StreamBuilder ISN'T going to be the last thing#it's just part of it#my guess is it is the part they managed to wrangle enough stable enough comparatively to do so#and they just... need to wrangle the code of other parts of tumblr into something more open source manageable#it's probably never going to be the WHOLE site or EVERYTHING about it opensource but#i'm guessing there will be more parts opened up. probably?
3 notes
·
View notes
Text
The Trunk Line
New personal blog post - some background on the Trunk & Tidbits blog series that I've been helping to deliver for the Mastodon team... #blaugust2024 #100DaysToOffload
One of my freelance roles at the moment is as Developer Relations lead on the Mastodon project. It is a project and platform I’m really passionate about – I use it every day, it is Open Source and based on an open standard, and I strongly feel that federated platforms like this are the key to enabling everyone to own their own content, networks, and experiences beyond the direct reach of…
#Blaugust2024#100DaysToOffload#activitypub#Coding#community#developer relations#developers#devrel#fediform#fediverse#mastodon#open source#oss#project management#trunk & tidbits
0 notes
Text
Github, Wow! 😍
Seriously, you got me. I don't have many code-based projects outside of my own personal stuff so I don't use Github like a true developer. I do tinker and bop around in it.
I'm an avid fan of Gitbooks, but I happen to stumble upon the project management feature in Github and now I'm obsessed.
I want to just check out all of the github stuff and play with it today. However, it is Thursday which means I am "working" and I should be focusing on that.... Well, I'll try lol.
#github#technology#tech#girl dev#code#girl code#computers#open source#programming#apps#software#project management#developer#operations#iot#iot tech#internet finds#tech community#gitbook#gitlab#productivity#planning#wfh#wfhlife#introvert#tech enthusiasts#coding#developers#web design#workspace
1 note
·
View note
Text
I dress like as much of a freak as I can get away w without breaking the dress code at work so that the baby freaks who come thru feel comfortable
#I’d post a pic but I am Highly Recognisable#source: just trust me dude#I am breaking the dress code a bit tbh but the managers don’t care bc I’m an important member of the team and they’re not gonna split hairs
1 note
·
View note
Note
🔥 open source
The benefits of open source code are only as valuable as you can make of them and everyone who diminishes the value of FOSS just has a skill issue. The sheer power you have over any piece of software with open source code is unimaginable if you are actually a good enough developer that you're able to use it.
The conclusion of this is that FOSS doesn't matter to normies. Sure often times FOSS has better privacy or compatibility but for someone who isn't a developer open source software has no inherent benefit over closed source software. Open-source isn't a selling point to normal people.
#thanks for the ask!#i love foss#ill never forget the day i tracked down a crash in my system by grepping the linux source code#and i actually managed to fix it#you could never come close to doing that with closed source software
1 note
·
View note
Text
Health Code Violation- DC x DP prompt
"Hold on there. You're not permitted beyond this point." The floating teenage boy said as he tucked his clipboard under his arm.
After a battle with another world-ending villain Superman was killed in action and after a short debate the decision to revive him using the Lazarus Pit was made. However, the league members who were carrying his body to the pit didn't expect it to be blocked off with caution tape. A teenage boy with stark white hair and wearing a hard hat and orange construction vest.
"What are you doing out here kid? And what is with the tape?" Barry asked shifting Clark's heavy ass body from crushing him.
"I'm here to take a look at the leak." He said pointing a thumb in the direction of the green pit.
"The leak?" Diana echoed in confusion.
"Yeah, your planet has a leak. A few actually. Our realm hasn't been managed well and now that the old king is gone we need to fix some things. Right now the leaks need to be sealed." He said. "Also what's with the dead guy?"
"We were bringing him to the Lazarus Pit to revive him." Barry said blankly.
The teen shook his head in astonishment almost dropping his clipboard.
"You are what?! With the what?!"
"The Lazarus pit...?" Hal laughed nervously his face in a half-quirked smile.
"You call it a Lazarus Pit? Guys this is a pool of contaminated ectoplasm. Basically sewage. This thing is full of dead people juice. All those leftover emotions and obsessions are stewing in there. You toss that body in these pool and you'll make a revenant full of anger. It doesn't even have an ecosystem to cleanse it. It's like stagnant water." The teen said waving his pen around before pausing "Wait a minute....you people have been using it? No wonder it's so polluted! What is wrong with you?! Are you trying to contaminate your planet? Do you want zombies?"
It was kind of weird to be scolded by a kid, for everyone but Bruce. He thought of a more pragmatic approach. He didn't like the pit but he acknowledged it's usefulness.
"I understand. But we do want to save our friend and the only way is to use the pit."
"That's a big ask. The pit is one thing but bringing back the dead willy nilly? ...But I guess that's my domain now.. "
The teen mumbled to himself before sighing.
"Look, I want to help. I really do. But the pit is unstable and there are many more on this planet with the same issue. We can't risk an apocalypse and the chance they get into the wrong hands. This is for the safety of your planet." The teen said as mannerly as possible as he dismissed the heros.
"Come on, please. Our friend is dead. You don't want our friend to die." Barry said pleadingly.
"Very mature of you. A bit of shame might help you...alright fine but don't badger me again." The silver-haired being said taking out a small syringe and taking a sample of his own blood.
"It's diluted compared to the pure stuff but 10x stronger than the stuff in the pool. It's safer and once he's kicking again it'll drain out of his system." He tossed the needle to Barry and returned to taking samples of the pit. "This biohazard requires an ecologist. I'll have to import some blob feeders to clean up the toxins. Then either seal this up or link it to the network. But these dumb mortals are just going to keep dumping bodies into it."
The teen mumbled to himself as he tried to find a solution.
A week later all the Lazarus pits had disappeared. The Al Ghuls were scrambling as the source of their powers dried up.
Clark was alive and feeling better than ever. No pit rage at all.
Eventually the boy returned.
"I had a talk with the ancients and they agreed to let you have one ecto pool. Only one thought and it has to be managed by me. As long as you don't try abusing it by going into it while alive or not asking permission I'll allow you to use it. Also, be mindful of my cleaning wisps, they work very hard to keep the natural flow of the ecto cycle going." The teen said holding up a green little ghost blob and petting it.
#what should i name the little blobs#i know danny named each one#dpxdc#dc x dp#dc x dp prompt#danny fenton#danny phantom#dp x dc prompt
1K notes
·
View notes
Text
IDIA MADE AN AMV TO EXPLAIN HIS PLAN TO YUU AND FRIENDS IU'M FUCKING DYING
HE EVEN HAS A GOD DAMN NARRATION OMFG
"Ahh~ Only good things are happening lately~ As if we're in a dream~"
"Eh. It's actually just a dream tho."
"Hello everyone trapped in this empty world of dreams."
"This is Idia Shroud."
"So today, I will explain the strategy to beat:
"I BUILT A DREAM WORLD USING CHEAT-LEVEL MAGIC AS THE MOST EVIL LAST BOSS MAGE MALLEUS DRACONIA"
"The magical domain that Malleus created is similar to a server running a huge MMORPG."
"That means everyone's dreams are ran individually. Malleus and his clones are keeping an eye on the server."
"In other words, Malleus is the server admin."
"And his clones crack down on users who commit violations like in online games."
"Malleus is the game master who has the authority to manage the entire server."
"HE REALLY IS A DEMON LORD WHO RULES THE WORLD"
"Under his control, we have no chance of winning..."
"HOWEVER..!"
"With the super geek hacker group STYX using ORTHO ATTACK, the server source code has been analyzed."
"So using this, we're building cheating tools [WARNING: DO NOT DO THIS IN ACTUAL GAMES]"
"So using these cheating tools, the administrative rights to my dream can be transferred to me."
"Then I'll lure Malleus into my dream where I can get rid of that god damned invincibility!"
I CAN'T FUCKING TAKE THIS OH MY GOD
"-- Well, it sounds like a perfect strategy but... The truth is there's just a few things about this cheating tool..."
"WHAT IF THE SERVER ADMIN FINDS OUT ABOUT THIS DURING DEVELOPMENT?"
"THEN,"
"GAME OVER."
"BUT BUT BUT--"
"The thing is, even though he's using autonomous clones to monitor each dream, it still shouldn't be easy to control the dreams of 20000 PEOPLE in Sage island."
"If problems turn up everywhere, he'll have to deal with them all!"
"Sooooo..."
"While I'm developing the cheat tool, I want you all to distract Malleus!"
"I want you all to gather party members to defeat the Demon King!"
"Once everyone's awake, I'll send out invitations to my own dream."
"Then I'll lure Malleus into my dream... THEN TURN ON THE CHEAT TOOL! As planned, Malleus' invincibility will disappear,"
"Then everyone will accept the invitation and gather into my dream!"
"THEN EVERYONE BEATS HIM UP"
"Then Malleus will have to take down his magic AND EVERYONE WILL BE FREE!"
"If you liked this 3-minute video, don't forget to leave a like!"
I'M GONNA FUCKING CRY THIS IS INSANE OMFG KASDJLKLDASLMASD
6K notes
·
View notes
Text
Still standing
On the afternoon of April 14th, a hacker using a UK IP address exploited an out-of-date software package on one of 4chan's servers, via a bogus PDF upload. With this entry point, they were eventually able to gain access to one of 4chan's servers, including database access and access to our own administrative dashboard. The hacker spent several hours exfiltrating database tables and much of 4chan's source code. When they had finished downloading what they wanted, they began to vandalize 4chan at which point moderators became aware and 4chan's servers were halted, preventing further access.
Over the following days, 4chan's development team surveyed the damage, which to be frank, was catastrophic. While not all of our servers were breached, the most important one was, and it was due to simply not updating old operating systems and code in a timely fashion. Ultimately this problem was caused by having insufficient skilled man-hours available to update our code and infrastructure, and being starved of money for years by advertisers, payment providers, and service providers who had succumbed to external pressure campaigns.
We had begun a process of speccing new servers in late 2023. As many have suspected, until that time 4chan had been running on a set of servers purchased second-hand by moot a few weeks before his final Q&A, as prior to then we simply were not in a financial position to consider such a large purchase. Advertisers and payment providers willing to work with 4chan are rare, and are quickly pressured by activists into cancelling their services. Putting together the money for new equipment took nearly a decade.
In April of 2024 we had agreed on specs and began looking for possible suppliers. Money is always tight for us, and few companies were willing to sell us servers, so actually buying the hardware wasn’t a trivial problem. We managed to finalize a purchase in June, and had the new servers racked and online in July. Over the next few months we slowly moved functionality onto the new servers, but we had still been relying on the old servers for key functions. Everything about this process took much longer than intended, which is a recurring theme in this debacle. The free time that 4chan's development team had available to dedicate to 4chan was insufficient to update our software and infrastructure fast enough, and our luck ran out.
However, we have not been idle during our nearly two weeks of downtime. The server that was breached has been replaced, with the operating system and code updated to the latest versions. PDF uploads have been temporarily disabled on those boards that supported them, but they will be back in the near future. One slow but much beloved board, /f/ - Flash, will not be returning however, as there is no realistic way to prevent similar exploits using .swf files. We are bringing on additional volunteer developers to help keep up with the workload, and our team of volunteer janitors & moderators remains united despite the grievous violations some have suffered to their personal privacy.
4chan is back. No other website can replace it, or this community. No matter how hard it is, we are not giving up.
585 notes
·
View notes
Text
📷 request from anon! kuroo surprising you and kenma at your house at the crack of dawn on your 5th anniversary, filming the moment on stream for all of his fans to see (post-timeskip kenma! x reader)
“happy fifth anniversary!”
kuroo’s voice startles you awake as you’re laying in bed. you sit up, a little bit disoriented, kenma’s sleeping figure still holding you tight in his arms. you look around frantically to find the source of the loud exclamation. what is kuroo’s voice doing in your house so early in the morning? as you observe your surroundings you notice that the sun is still rising, with small beams of orange light peering into the bedroom through the curtains. the light illuminates the room through the awfully thin and cheap fabric—you and kenma had bought them for temporary use while first moving in and haven’t bothered to change them since.
your eyes manage to focus as they pinpoint a large bird’s nest of black hair, the figure that dawns it leaning over the two of you with a camera shoved obnoxiously in your faces. “good morning love birds!” kuroo cheers, zooming his phone in onto kenma’s face as he wakes. “look at this chat, kenma acting like such a cutie pie, oh my goodness! isn’t this adorable?! snuggled up to the love of his life!”
kenma leans over to check the time on his nightstand, groaning as he reads 5:30 A.M. “kuroo, it’s 5 in the fucking morning. on a saturday. you asshole.”
“how did he even get in our house?” you ask kenma, a little worried and a whole lot confused.
“gave him the garage code when he left his shit here on new year’s,” he replies, voice grainy and scratchy as he rubs his hand across his face. he mumbles something along the lines of gonna have to change that before noticing the device in kuroo’s hands, freezing mid-movement. “are you recording us?”
“live streaming for your fans.”
“huh?!” both you and your boyfriend yell in unison. kenma instinctively shoves his hand in front of the camera, blocking the view of your bed heads and disheveled pajamas.
“hmm? is the ceo of bouncing ball corp camera shy?” kuroo’s voice is laced with a teasing tone, grin all smug as he shines his teeth wide across his face.
“no, but you’re filming y/n too. i’m sure she didn’t give you permission to do that at the ass crack of dawn.” he pulls the blanket over you more as if that’ll somehow help shield you from the camera that’s already captured the moment for the whole world to see. yawning, he rubs the back of his neck and groggily runs a hand through his hair. he’s not a big morning person, acting irritated at best during the early hours of the day. but of course, that’s just one way kuroo had planned to push his buttons with his master plan of breaking into your shared home.
“well, since i’m recording this big milestone for your anniversary, why don’t you take out that nice velvet ring b—”
“okay, that’s enough!” kenma yells, grabbing the phone out of kuroo’s grip and slapping his hand across his mouth to effectively cut him off. “you’re such an asshole kuroo!”
you turn under the sheets, curling against kenma’s side. “hmm? what box?”
“nothing, love.” kenma murmurs softly to you, pushing your messy hair back from your forehead before slapping kuroo across the back. “go home, stream’s over pisshead.” as kuroo winces from the impact, kenma pulls the covers further over both of you and pulls you back against his chest. it’s a moment that kuroo doesn’t waste a second to capture, seizing the opportunity for more publicity. the quick shot of it he sneaks for the chat is one they have a total field day with. when kenma sees the clips of it online later that day, he smiles to himself as he can only imagine how much crazier their reactions would have been if they saw the way he fiddled with your ring finger under the sheets, running his finger in a circular motion around it as if imitating the band of a ring.
(he’ll have to pop the question soon, before kuroo ends up actually spoiling the surprise.)
masterlist + taglist + tags: @scoupsworld @mires765 @amaliaaliena @nanasrkives
© evamame 2025. all rights reserved. please do not repost, modify, steal, plagiarize, or translate my work.
#eva’s fantasies 𓍼 ོ☁︎#kenma kozume x reader#haikyuu!! kenma kozume#hq kenma#kenma x reader#haikyuu kenma#kozume kenma#kenma#kenma x you#kenma x y/n#kenma kozume x you#kenma kozume x y/n#kozume x reader#haikyuu kozume#kenma kozume#kenma fluff#kenma fanfic#kenma kozume fluff#haikyuu#haikyuu!!#haikyu#hq#haikyuu time skip#haikyuu x reader#hq x reader#hq fluff#hq x you#haikyuu crack#hq x y/n#haikyuu x y/n
681 notes
·
View notes
Text
tracking barbara gordon's skillset as oracle:
she provides directory assistance for several international and intergalactic teams of superheroes (the birds of prey, justice league of america, the outsiders, and she has worked with the titans before).
she is the primary hacker and information network source for many of these heroes.
she helps provide mercy ops (disaster relief and humanitarian efforts) globally.
she is able to hack into the white house cameras.
she hacks into the united states air force routinely to use their memory capabilities.
she is seen as a pentagon level threat.
she writes her own code for scanning new satellite images for human habitations and anomalies.
she's accessed air force rockets no one is supposed to know about and overridden them to fire them.
she has a team of drones ready for surveillance.
she's put her own security systems on arkham asylum.
she hacks into information databases from federal complexes and assembles blueprints and guard schedules so she can send her agents to break into them.
she sets a government complex on fire (she says it is a small and contained fire.)
she also sets the clock tower on fire to force batman to not do murder/suicide.
she hacks into cia debriefing transcripts to obtain information.
she controls a large portion of the world's internet and power grids.
she also is the reason why many world leaders are in power.
she has access to the bank accounts of several supervillains, whom she toys with (specifically for blockbuster, she regularly steals millions of dollars from his accounts in a way that he cannot track who is stealing it and where it is going -- she's stolen 3 million, 17 million, 6 million, twenty million and also a hundred million from him).
she can also hack alien drones.
she can control traffic.
she has several booby-traps in the clock tower for potential assaulters. she also a device to monitor movement of people around it, in case batman decides to show up.
cited panels down below!
"she's the four-one-one for the jla, she the database for the g.c. ex-p.d. she runs mercy ops around the world." nightwing (1996) #38
"you have cameras in the white house?" "don't be silly. the white house has cameras in the white house. i've just tapped into them." nightwing (1996) #66
"i mean, someone hacks into our system and routinely uses our [united states air force] memory capabilities!" "i know!" "often." birds of prey #1 (1999)
"i run a database and search engine for a select few free-land crimefighters." birds of prey: manhunt (1996)
"we scan the most recent images for anomalies. things that don't belong." "where'd you get a program for that?" "i wrote my own code for that one." birds of prey (1999) #3
"they've accessed whitehorse, sir." "whitehorse? no one's supposed to know about that!" birds of prey (1999) #9
"and oracle? we're going to need eyes on several places at once." "i think we can manage that." detective comics (1937) #1077
"they've accessed whitehorse. what's the chance of them arming it?" "all clear?" "oh yeah." "fire!" birds of prey (1999) #9
"[arkham's] security is good, but piecemeal. i installed my own system there after the last breakout." infinite crisis special: villains united (2006)
"batgirl -- that incident a couple months back? when those government agents caught your face on tape? i found out where they're keeping it. it's a federal complex in virginia. i've sent you blueprints, guard schedules -- everything you'll need to break in." batgirl (2000) #17
"where did you get that kind of information?" "they traded another prisoner last month. i hacked into his cia debriefing transcript." birds of prey (1999) #9
"kat, do you have any idea... any notion at all, of how much of the planet's entire internet i control? how many power grids? how many world leaders owe me their positions?" birds of prey #1 (1999)
"i transferred all the funds in her cayman islands account to another offshore account. if she doesn't get the paintings to me in the next forty-eight hours, that money's going to my favorite charities." birds of prey: catwoman/oracle (2003)
"where do you get current [satellite] shots of rheelasia?" "that's my secret, you little netnik." birds of prey (1999) #3
"but the asborbascons were created using languages long dead even on my planet. they are uncrackable." "yes. the absorbascons are uncrackable. but the alien drones aren't." convergence: nightwing/oracle (2015)
"do you have that kind of cash?" "no. but i know someone who does." "there's been a... discrepancy, mr. desmond." "in plain english, mr. vogel." "at one point, three million was electronically transferred from your numbered accounts in the caicos to a bank account in hasaragua. from there to karocco, then yemen, then split between banks in senegal and manila. and then... my hardware couldn't keep up." birds of prey (1999) #3
"seventeen million from your account in the caymans. six from santa prisca. twenty from rheelasia. and a hundred million plus from other holdings of yours around the world, mr. desmond. and where it all goes? nobody knows." birds of prey (1999) #18
"they're taking your cash from impregnable accounts and transferring it electronically to their own." "and you can't find the source?" "there's subsequent transfers performed at lightning speed. the money's split up, rerouted in and out of various banks in an eyeblink. even i can't keep up with whoever this is." birds of prey (1999) #18
"let me handle the traffic." birds of prey (1999) #58
"all of you. keep your hands where i can see 'em." "not a problem. malory. ripken. peppermint." nightwing (1996) #39
#barbara gordon#babs#oracle#batgirl#birds of prey#justice league of america#jla#batman#robin#nightwing#huntress#black canary#blockbuster#dick grayson#tim drake#helena bertinelli#bruce wayne
446 notes
·
View notes
Text
Hey: the Twitter "leak" about Twitter letting certain alt-right users say slurs? It's a fake.
There's no source or attribution, no way to verify it.
Additionally, it says it's from okta: okta is a login/identity management system, used by a lot of companies. Twitter is not one of those companies!
There's no reason for any Twitter code to be dealing with okta.
Also, okta is a configurable platform, where each company can set their own policies and requirements. Because of that, you can look up the docs on how you'd configure this kind of permissions in okta, and it doesn't look like this. The syntax is wrong.
Someone just made up a mock file to back up a lie about Twitter being shitty (don't get me wrong: Twitter is shitty and is doing lots of terrible things: this isn't one of them)
1K notes
·
View notes